[JAVA-6159] Micrometer feedback by nhachicha · Pull Request #1940 · mongodb/mongo-java-driver

nhachicha · 2026-04-13T11:03:34Z

AI Usage Summary

Claude-Caude with Opus 4.6 1M Model

What AI did well

Research & synthesis — Fetched and synthesized feedback from 3 external sources (Jonatan's gist, Spring Boot issue, Spring Data ContextProviderFactory) into a structured plan
Test-first approach — Wrote failing tests before implementing fixes, following the user's guidance
Mechanical refactoring — Renaming imports, splitting enums, updating call sites across multiple files
Cross-referencing open source — Researched Lettuce, R2DBC, and Spring WebFlux patterns for reactive context propagation
Explaining concepts — Broke down Micrometer Observation vs Tracing API, scope mechanics, Reactor context propagation

Where the user corrected or pushed back

Situation	What happened
Reducing tag duplication	AI implemented a `CommonLowCardinalityKeyNames` refactor; user asked for suggestion only, not implementation — had to revert
Removing imperative tagging	AI initially kept both imperative tags AND context fields (duplication); user spotted the redundancy and pushed to remove all imperative calls
`tagHighCardinality` in InternalStreamConnection	AI claimed the remaining imperative calls were necessary; user pointed out they could go through `getMongodbContext()` instead
Scope in TransactionSpan	AI put `openScope()` in the constructor (shared by sync+reactive); user asked why scope is public — led to discovering it should only be called from sync
Reactive context propagation	AI spent multiple iterations trying `contextWrite`, `contextCapture`, `AtomicReference` patterns — all failed due to `Mono.from(subscriber -> ...)` pattern. User questioned
each attempt
`Hooks.enableAutomaticContextPropagation`	AI assumed version alignment would fix it; user actually tried it and reported the hang, forcing deeper investigation
Reactive driver refactor scope	After extensive async work, user asked if `context-propagation=auto` alone would suffice — AI confirmed, user decided to stash reactive changes and keep it simple
commit transaction reactive failure	AI tried to skip the test; user rejected and demanded root cause investigation — led to finding the OTel bridge scope leak from `TransactionSpan` constructor
Modifying stopped observations	AI removed parent cursor_id mutation; user showed Zipkin traces proving it broke nesting — led to reverting, then user suggested removing it properly since parenting
works via `operationSpan.context()`
Test validation gaps	User commented out `contextWrite` and `contextCapture` to prove tests still passed — exposed that tests weren't actually validating the code they claimed to test
CheckStyle/SpotBugs	AI fixed checkstyle issues; user asked to revert since they only wanted suggestions, not implementation

The driver used a single observation name ("mongodb") for both operation-level and command-level spans, which have different sets of low-cardinality tag keys. Prometheus requires all meters sharing a name to have identical tag key sets, causing the second observation type to be silently dropped. Split MongodbObservation.MONGODB_OBSERVATION into MONGODB_OPERATION (name "mongodb.operation") and MONGODB_COMMAND (name "mongodb.command"), each declaring its own low-cardinality key set. Updated Tracer and TracingManager to pass the observation type through span creation.

Connection IDs, cursor IDs, session IDs, transaction numbers, and exception details were tagged as low-cardinality, causing unbounded Prometheus metric cardinality since their values change per-connection, per-cursor, or per-error. Moved CLIENT_CONNECTION_ID, SERVER_CONNECTION_ID, CURSOR_ID,TRANSACTION_NUMBER, SESSION_ID, EXCEPTION_MESSAGE, EXCEPTION_TYPE, and EXCEPTION_STACKTRACE from CommandLowCardinalityKeyNames to HighCardinalityKeyNames so they appear only in traces, not in metrics. Added tagHighCardinality(KeyValue) and tagHighCardinality(KeyValues) to the Span interface to support string-valued high-cardinality tags alongside the existing BsonDocument overload.

The query text max length configuration constant was stored in every Observation.Context and extracted back in the MicrometerSpan constructor. This value never changes between observations and is not output as any signal. Pass it directly via constructor parameter instead.

Observations were created with Micrometer's generic SenderContext, preventing users from filtering or customizing MongoDB observations by context type. This blocks the ObservationConvention pattern that Spring Boot needs for tag alignment. Introduced MongodbContext extending SenderContext<Object> with Kind.CLIENT, giving users a MongoDB-specific type to register ObservationHandler<MongodbContext> or ObservationConvention<MongodbContext> instances scoped to only MongoDB observations.

…f TracingManager Replaced all imperative tagLowCardinality/tagHighCardinality calls with a convention-based approach. TracingManager and InternalStreamConnection now populate domain fields on MongodbContext, and DefaultMongodbObservationConvention reads those fields at stop time to produce the final key-values. This decouples tag naming from span creation, enabling users to register a GlobalObservationConvention<MongodbContext> to customize tag names for their environment (e.g. Spring Boot tag alignment with their existing DefaultMongoCommandTagsProvider). Added domain fields to MongodbContext: observationType, commandName, databaseName, collectionName, serverAddress, connectionId, cursorId, transactionNumber, sessionId, queryText, responseStatusCode. Removed tagLowCardinality/tagHighCardinality from the Span interface as they are no longer used.

Update attribute name for OpenTelemetry

The driver called observation.start()/stop() but never openScope()/ closeScope(). Without scopes, registry.getCurrentObservation() returned null during MongoDB operations, breaking context propagation for any downstream code (Spring interceptors, user observations, MDC logging). For example, in withTransaction, a user observation created inside the callback would attach to the Spring HTTP parent instead of the MongoDB transaction span, because the transaction observation was never made "current" on the thread. Added openScope()/closeScope() to the Span interface with scope lifecycle management in MongoClusterImpl (operation spans), InternalStreamConnection (command spans), and TransactionSpan.

When a getMore command arrived, the cursor_id was being set on the parent operation span's MongodbContext even though the parent observation was already stopped. Modifying an observation after stop() is undefined behavior in Micrometer

Copilot

Pull request overview

Refactors Micrometer-based tracing to align better with OpenTelemetry/Micrometer conventions by separating operation vs command observations, moving tag production into an ObservationConvention, and introducing explicit span scope management in sync execution paths.

Changes:

Split MongoDB observations into distinct operation- and command-level observation types to avoid tag-keyset collisions (e.g., Prometheus restrictions).
Replace imperative tagging with a MongodbContext + DefaultMongodbObservationConvention that derives tags from populated domain fields.
Add explicit openScope() / closeScope() lifecycle handling for spans in sync execution code paths and update unified test modifications accordingly.

Reviewed changes

Copilot reviewed 15 out of 15 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
driver-sync/src/test/functional/com/mongodb/client/unified/UnifiedTestModifications.java	Updates unified test skip rules for OpenTelemetry/Micrometer-related specs.
driver-sync/src/test/functional/com/mongodb/client/unified/Entities.java	Minor formatting adjustment in Micrometer observability settings setup.
driver-sync/src/test/functional/com/mongodb/client/observability/SpanTree.java	Updates test tag-key imports to match new low/high-cardinality key enums.
driver-sync/src/main/com/mongodb/client/internal/MongoClusterImpl.java	Opens/closes span scope around sync operation execution.
driver-sync/src/main/com/mongodb/client/internal/ClientSessionImpl.java	Opens transaction-span scope when starting a transaction (sync).
driver-core/src/main/com/mongodb/internal/observability/micrometer/TransactionSpan.java	Ensures transaction span scope is closed before ending in finalization paths; adds `openScope()` API.
driver-core/src/main/com/mongodb/internal/observability/micrometer/TracingManager.java	Switches span creation to operation vs command observation types and populates `MongodbContext` fields for conventions.
driver-core/src/main/com/mongodb/internal/observability/micrometer/Tracer.java	Updates tracer API to accept an observation type when creating spans.
driver-core/src/main/com/mongodb/internal/observability/micrometer/Span.java	Replaces tag APIs with scope management + query-text setting + context access.
driver-core/src/main/com/mongodb/internal/observability/micrometer/MongodbObservation.java	Splits key names into operation vs command low-cardinality sets and reorganizes high-cardinality keys.
driver-core/src/main/com/mongodb/internal/observability/micrometer/MongodbContext.java	Introduces a MongoDB-specific Micrometer `SenderContext` to hold domain fields used by conventions.
driver-core/src/main/com/mongodb/internal/observability/micrometer/MicrometerTracer.java	Uses `MongodbContext`, registers the default convention, and implements new `Span` API.
driver-core/src/main/com/mongodb/internal/observability/micrometer/DefaultMongodbObservationConvention.java	New default global convention that emits tags from `MongodbContext` fields (including errors).
driver-core/src/main/com/mongodb/internal/connection/InternalStreamConnection.java	Uses new `Span` API, populates query text/status code via `MongodbContext`, and opens/closes scope around command spans.
config/checkstyle/suppressions.xml	Moves the `printStackTrace` suppression to the new convention class.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Move openScope() calls after code that can throw to prevent scope leaks on early exceptions in MongoClusterImpl (binding creation) and InternalStreamConnection (command setup). Update createTracingSpan Javadoc to reflect convention-based tagging.

…ntion - Renamed MongodbContext to MongodbObservationContext and moved it along with DefaultMongodbObservationConvention to the public package com.mongodb.observability.micrometer - Added observationConvention() to MicrometerObservabilitySettings so users can provide a custom convention - Added testCustomObservationConvention to AbstractMicrometerProseTest validating that a user-provided convention fully controls tag output

Copilot

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 2 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 2 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

…ervationContext

Copilot

Pull request overview

Copilot reviewed 22 out of 22 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

driver-core/src/main/com/mongodb/internal/connection/InternalStreamConnection.java:464

createTracingSpan(...) unconditionally calls commandDocumentSupplier.get() (to determine command name / sensitivity). When command logging or command-payload tracing is also enabled, sendAndReceiveInternal then calls message.getCommandDocument(bsonOutput) again, causing the command document to be reconstructed twice from the same encoded buffers. Consider hydrating the BsonDocument once and reusing it for both tracing-span creation and logging/payload (e.g., via a memoized supplier or by passing the already-built document into tracing).

            tracingSpan = operationContext
                    .getTracingManager()
                    .createTracingSpan(message,
                            operationContext,
                            () -> message.getCommandDocument(bsonOutput),
                            cmdName -> SECURITY_SENSITIVE_COMMANDS.contains(cmdName)
                                    || SECURITY_SENSITIVE_HELLO_COMMANDS.contains(cmdName),
                            () -> getDescription().getServerAddress(),
                            () -> getDescription().getConnectionId()
                    );
            boolean isLoggingCommandNeeded = isLoggingCommandNeeded();
            boolean isTracingCommandPayloadNeeded = tracingSpan != null && operationContext.getTracingManager().isCommandPayloadEnabled();

            // Only hydrate the command document if necessary
            BsonDocument commandDocument = null;
            if (isLoggingCommandNeeded || isTracingCommandPayloadNeeded) {
                commandDocument = message.getCommandDocument(bsonOutput);
            }

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-17T14:19:01Z

 import com.mongodb.internal.session.SessionContext;
 import com.mongodb.lang.Nullable;
 import com.mongodb.observability.ObservabilitySettings;
+import com.mongodb.observability.micrometer.DefaultMongodbObservationConvention;


DefaultMongodbObservationConvention is imported but only referenced in Javadoc. Checkstyle's UnusedImports check will still flag this as an unused import and fail the build. Remove the import and use a fully-qualified type in the Javadoc (or reference it from code).

Suggested change

import com.mongodb.observability.micrometer.DefaultMongodbObservationConvention;

Copilot

Pull request overview

Copilot reviewed 22 out of 22 changed files in this pull request and generated 2 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-17T15:04:23Z

@@ -427,8 +427,9 @@ public <T> T execute(final ReadOperation<T, ?> operation, final ReadPreference r
            Span span = operationContext.getTracingManager().createOperationSpan(
                    actualClientSession.getTransactionSpan(), operationContext, operation.getCommandName(), operation.getNamespace());


createOperationSpan(...) is currently always given actualClientSession.getTransactionSpan(), even when actualClientSession.hasActiveTransaction() is false. Since ClientSessionImpl retains the last transactionSpan after commit/abort, this will incorrectly parent subsequent non-transaction operations under an already-finished transaction span. Pass the transaction span only when the session has an active transaction (or update getTransactionSpan() to return null when inactive) so trace nesting is correct.

Suggested change

actualClientSession.getTransactionSpan(), operationContext, operation.getCommandName(), operation.getNamespace());

actualClientSession.hasActiveTransaction() ? actualClientSession.getTransactionSpan() : null,

operationContext, operation.getCommandName(), operation.getNamespace());

Copilot · 2026-04-17T15:04:24Z

        if (tracingManager.isEnabled()) {
            transactionSpan = new TransactionSpan(tracingManager);
+            transactionSpan.openScope();
        }


transactionSpan is created (and now has its scope opened) in startTransaction(...), but it is never cleared when the transaction is finished. Because other code paths pass getTransactionSpan() into operation span creation, a committed/aborted transaction span can remain as the parent for later non-transaction operations within the same session. Consider clearing transactionSpan when transitioning out of an active transaction (e.g., in cleanupTransaction(...) / after commit+abort), and/or make getTransactionSpan() return null when !hasActiveTransaction().

Copilot

Pull request overview

Copilot reviewed 22 out of 22 changed files in this pull request and generated 2 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-17T15:40:59Z

    public Span addTransactionSpan() {
-        Span span = tracer.nextSpan("transaction", null, null);
-        span.tagLowCardinality(SYSTEM.withValue("mongodb"));
-        return span;
+        return tracer.nextSpan(MONGODB_OPERATION, "transaction", null, null);
    }


addTransactionSpan() creates the transaction span as a MONGODB_OPERATION observation, but the driver never populates operation domain fields (db namespace / collection / operation name / summary) for transactions. With DefaultMongodbObservationConvention, this will emit a different set of tag keys for mongodb.operation when the span represents a transaction vs a normal operation, which can reintroduce Prometheus meter rejection due to inconsistent label-name sets for the same metric name.

Consider introducing a dedicated observation type for transactions (e.g., mongodb.transaction with its own fixed key set), or populating the operation fields for the transaction span so mongodb.operation observations are consistent.

Copilot · 2026-04-17T15:41:00Z

        final MicrometerObservabilitySettings that = (MicrometerObservabilitySettings) o;
        return enableCommandPayloadTracing == that.enableCommandPayloadTracing
-                && Objects.equals(observationRegistry, that.observationRegistry);
+                && Objects.equals(observationRegistry, that.observationRegistry)
+                && Objects.equals(observationConvention, that.observationConvention);
    }

    @Override
    public int hashCode() {
-        return Objects.hash(observationRegistry, enableCommandPayloadTracing);
+        return Objects.hash(observationRegistry, enableCommandPayloadTracing, observationConvention);
    }


equals/hashCode ignore maxQueryTextLength. This means two MicrometerObservabilitySettings instances that differ only by query-text truncation settings will compare equal and hash to the same bucket, which can lead to incorrect behavior if these settings are ever used as keys (e.g., caching, deduplication, tests).

Include maxQueryTextLength in both equals and hashCode (and consider whether other fields should also participate) so object equality reflects the full configuration.

Copilot

Pull request overview

Copilot reviewed 22 out of 22 changed files in this pull request and generated 2 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-17T15:58:02Z

+    @SuppressWarnings("NullableProblems")
+    @Test
+    void testCustomObservationConvention() {
+        ObservationConvention<MongodbObservationContext> customConvention = new ObservationConvention<MongodbObservationContext>() {
+            @Override
+            public boolean supportsContext(final Observation.Context context) {
+                return context instanceof MongodbObservationContext;
+            }
+
+            @Override
+            public KeyValues getLowCardinalityKeyValues(final MongodbObservationContext context) {
+                String commandName = context.getCommandName() != null ? context.getCommandName() : "";
+                String databaseName = context.getDatabaseName() != null ? context.getDatabaseName() : "";
+
+                KeyValues kv = KeyValues.of(
+                        "db.system.name", "mongodb",
+                        "db.namespace", databaseName,
+                        "custom.tag", "custom-value");
+
+                if (context.getObservationType() == MongodbObservation.MONGODB_COMMAND) {
+                    // Rename: emit command name under "mongodb.command" instead of "db.command.name"
+                    kv = kv.and("mongodb.command", commandName);
+                }
+                if (context.getObservationType() == MongodbObservation.MONGODB_OPERATION) {
+                    kv = kv.and("db.operation.name", commandName);
+                }
+                return kv;
+            }
+        };
+
+        MongoClientSettings clientSettings = getMongoClientSettingsBuilder()
+                .observabilitySettings(ObservabilitySettings.micrometerBuilder()
+                        .observationRegistry(observationRegistry)
+                        .observationConvention(customConvention)
+                        .build())
+                .build();


testCustomObservationConvention doesn’t set ENV_OBSERVABILITY_ENABLED. Since other tests in this class mutate that env var and it’s only restored in @AfterAll, this makes the test order-/environment-dependent (it will fail when run in isolation or after a test that left the var disabled). Set ENV_OBSERVABILITY_ENABLED explicitly in this test (or reset it in @BeforeEach) to make the assertions deterministic.

Copilot · 2026-04-17T15:58:03Z

            Span span = operationContext.getTracingManager().createOperationSpan(
                    actualClientSession.getTransactionSpan(), operationContext, operation.getCommandName(), operation.getNamespace());
            ReadBinding binding = getReadBinding(readPreference, actualClientSession, implicitSession);
-
-
+            if (span != null) {
+                span.openScope();
+            }
            try {


span is created before getReadBinding(...). If getReadBinding (or getReadPreferenceForBinding) throws, the operation span is never ended (and never closed if scope was opened later), which can leave an Observation in a started-but-unended state. Consider restructuring so span lifecycle (openScope/closeScope/end and error tagging) is guaranteed via a try/finally that also covers binding acquisition failures (e.g., acquire binding inside the try and release/close/end in a finally that always runs once a span is created).

Copilot

Pull request overview

Copilot reviewed 22 out of 22 changed files in this pull request and generated 1 comment.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-17T17:09:31Z

    @Override
    public boolean equals(final Object o) {
        if (o == null || getClass() != o.getClass()) {
            return false;
        }
        final MicrometerObservabilitySettings that = (MicrometerObservabilitySettings) o;
        return enableCommandPayloadTracing == that.enableCommandPayloadTracing
-                && Objects.equals(observationRegistry, that.observationRegistry);
+                && Objects.equals(observationRegistry, that.observationRegistry)
+                && Objects.equals(observationConvention, that.observationConvention);
    }

    @Override
    public int hashCode() {
-        return Objects.hash(observationRegistry, enableCommandPayloadTracing);
+        return Objects.hash(observationRegistry, enableCommandPayloadTracing, observationConvention);
    }


MicrometerObservabilitySettings.equals / hashCode do not incorporate maxQueryTextLength. Two settings instances with different query text truncation behavior will compare equal and can collide in hash-based collections/caches. Include maxQueryTextLength in both equals and hashCode so equality reflects all configuration that affects behavior.

Copilot

Pull request overview

Copilot reviewed 22 out of 22 changed files in this pull request and generated no new comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot

Pull request overview

Copilot reviewed 22 out of 22 changed files in this pull request and generated 1 comment.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-17T19:25:40Z

+    private MongodbObservation observationType;
+    @Nullable
+    private String commandName;


MongodbObservationContext is a public API type (com.mongodb.observability.micrometer) but it exposes com.mongodb.internal.observability.micrometer.MongodbObservation via the observationType field/getter. This leaks an internal.* type into the public surface area and makes it hard to evolve internal observability types without breaking users. Consider introducing a public enum (e.g., MongodbObservationType { OPERATION, COMMAND }) in the public package, or moving MongodbObservation out of internal if it is intended to be user-consumable.

Copilot

Pull request overview

Copilot reviewed 22 out of 22 changed files in this pull request and generated 1 comment.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-17T19:56:13Z

+import com.mongodb.ServerAddress;
+import com.mongodb.annotations.Beta;
+import com.mongodb.annotations.Reason;
+import com.mongodb.connection.ConnectionId;
+import com.mongodb.internal.observability.micrometer.MongodbObservation;
+import com.mongodb.lang.Nullable;


MongodbObservationContext is a public API type (com.mongodb.observability.micrometer), but it exposes com.mongodb.internal.observability.micrometer.MongodbObservation in its public surface (getObservationType / setObservationType). That leaks an internal type into the public API, making it hard to evolve the internal enum without breaking users who write custom ObservationConventions. Consider introducing a public enum (e.g., MongodbObservationType in the same public package) or splitting into distinct public context subtypes for command vs operation observations so users don’t need to depend on com.mongodb.internal.*.

Copilot

Pull request overview

Copilot reviewed 22 out of 22 changed files in this pull request and generated 1 comment.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-17T20:06:18Z

        return enableCommandPayloadTracing == that.enableCommandPayloadTracing
-                && Objects.equals(observationRegistry, that.observationRegistry);
+                && Objects.equals(observationRegistry, that.observationRegistry)
+                && Objects.equals(observationConvention, that.observationConvention);
    }



equals/hashCode now account for observationConvention, but still ignore maxQueryTextLength. That means two settings instances with different query-text truncation can compare equal and collide in hash-based collections/caches. Include maxQueryTextLength in both equals and hashCode (and any other fields that define the settings’ behavior).

Copilot

Pull request overview

Copilot reviewed 22 out of 22 changed files in this pull request and generated 2 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-17T20:24:57Z

+import com.mongodb.ServerAddress;
+import com.mongodb.annotations.Beta;
+import com.mongodb.annotations.Reason;
+import com.mongodb.connection.ConnectionId;
+import com.mongodb.internal.observability.micrometer.MongodbObservation;


This public API class (com.mongodb.observability.micrometer.DefaultMongodbObservationConvention) imports com.mongodb.internal.observability.micrometer.MongodbObservation. That couples the public convention API to internal implementation details and forces users to depend on internal packages. Prefer a public observation-type enum/type (or move MongodbObservation out of internal) so custom conventions can be implemented without internal imports.

Copilot · 2026-04-17T20:24:58Z

 import com.mongodb.MongoClientSettings;
+import com.mongodb.observability.micrometer.MongodbObservationContext;
+import com.mongodb.internal.observability.micrometer.MongodbObservation;
 import com.mongodb.lang.Nullable;


This test validates the public observationConvention(...) API, but it needs to import com.mongodb.internal.observability.micrometer.MongodbObservation to distinguish command vs operation (context.getObservationType() == ...). That’s a sign the public convention/context API is still leaking internal types. After introducing a public observation-type enum in the Micrometer API, update this test to use that public type instead.

nhachicha self-assigned this Apr 13, 2026

nhachicha added 4 commits April 13, 2026 12:28

nhachicha force-pushed the nh/micrometer_spring_feedback branch from 9b4b0ad to bf91627 Compare April 14, 2026 09:48

nhachicha added 4 commits April 14, 2026 11:54

Fixes JAVA-6094

da4a3c1

Update attribute name for OpenTelemetry

Fixing tests

db5387c

nhachicha changed the title ~~WIP Micrometer feedback~~ [JAVA-6159] Micrometer feedback Apr 16, 2026

nhachicha marked this pull request as ready for review April 16, 2026 14:58

nhachicha requested a review from a team as a code owner April 16, 2026 14:58

nhachicha requested review from Copilot and rozza April 16, 2026 14:58

Copilot started reviewing on behalf of nhachicha April 16, 2026 16:33 View session

Copilot AI reviewed Apr 16, 2026

View reviewed changes

nhachicha added 3 commits April 17, 2026 10:29

Bumping Micrometer APIs to @beta

31c4ce2

nhachicha requested a review from Copilot April 17, 2026 12:21

Copilot started reviewing on behalf of nhachicha April 17, 2026 12:21 View session

Copilot AI reviewed Apr 17, 2026

View reviewed changes

Comment thread ...-core/src/main/com/mongodb/observability/micrometer/DefaultMongodbObservationConvention.java

Comment thread ...-core/src/main/com/mongodb/observability/micrometer/DefaultMongodbObservationConvention.java

nhachicha requested a review from Copilot April 17, 2026 12:45

Copilot started reviewing on behalf of nhachicha April 17, 2026 12:45 View session

Copilot AI reviewed Apr 17, 2026

View reviewed changes

Comment thread ...-core/src/main/com/mongodb/observability/micrometer/DefaultMongodbObservationConvention.java Outdated

Comment thread driver-core/src/main/com/mongodb/observability/micrometer/MongodbObservationContext.java

nhachicha added 2 commits April 17, 2026 14:54

Add new public observability classes to Scala API test exclusions

777c326

Fix null-safety in DefaultMongodbObservationConvention and MongodbObs…

be3108e

…ervationContext

nhachicha requested a review from Copilot April 17, 2026 14:11

Copilot started reviewing on behalf of nhachicha April 17, 2026 14:12 View session

Copilot AI reviewed Apr 17, 2026

View reviewed changes

nhachicha requested a review from Copilot April 17, 2026 14:55

Copilot started reviewing on behalf of nhachicha April 17, 2026 14:56 View session

Copilot AI reviewed Apr 17, 2026

View reviewed changes

nhachicha requested a review from Copilot April 17, 2026 15:34

Copilot started reviewing on behalf of nhachicha April 17, 2026 15:34 View session

Copilot AI reviewed Apr 17, 2026

View reviewed changes

nhachicha requested a review from Copilot April 17, 2026 15:50

Copilot started reviewing on behalf of nhachicha April 17, 2026 15:50 View session

Copilot AI reviewed Apr 17, 2026

View reviewed changes

nhachicha requested a review from Copilot April 17, 2026 17:03

Copilot started reviewing on behalf of nhachicha April 17, 2026 17:03 View session

Copilot AI reviewed Apr 17, 2026

View reviewed changes

nhachicha requested a review from Copilot April 17, 2026 17:22

Copilot started reviewing on behalf of nhachicha April 17, 2026 17:22 View session

Copilot AI reviewed Apr 17, 2026

View reviewed changes

nhachicha requested a review from Copilot April 17, 2026 19:18

Copilot started reviewing on behalf of nhachicha April 17, 2026 19:18 View session

Copilot AI reviewed Apr 17, 2026

View reviewed changes

nhachicha requested a review from Copilot April 17, 2026 19:48

Copilot started reviewing on behalf of nhachicha April 17, 2026 19:49 View session

Copilot AI reviewed Apr 17, 2026

View reviewed changes

nhachicha requested a review from Copilot April 17, 2026 19:58

Copilot started reviewing on behalf of nhachicha April 17, 2026 19:59 View session

Copilot AI reviewed Apr 17, 2026

View reviewed changes

nhachicha requested a review from Copilot April 17, 2026 20:19

Copilot started reviewing on behalf of nhachicha April 17, 2026 20:19 View session

Copilot AI reviewed Apr 17, 2026

View reviewed changes

		@@ -427,8 +427,9 @@ public <T> T execute(final ReadOperation<T, ?> operation, final ReadPreference r
		Span span = operationContext.getTracingManager().createOperationSpan(
		actualClientSession.getTransactionSpan(), operationContext, operation.getCommandName(), operation.getNamespace());

	actualClientSession.getTransactionSpan(), operationContext, operation.getCommandName(), operation.getNamespace());
	actualClientSession.hasActiveTransaction() ? actualClientSession.getTransactionSpan() : null,
	operationContext, operation.getCommandName(), operation.getNamespace());

Conversation

nhachicha commented Apr 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Claude-Caude with Opus 4.6 1M Model

What AI did well

Where the user corrected or pushed back

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

nhachicha commented Apr 13, 2026 •

edited

Loading